Skip to content

Commit d4e3162

Browse files
samantharamonsamantharamon
authored
[All hosts] Get latest (#2381)
1 parent 6c3194b commit d4e3162

File tree

22 files changed

+503
-0
lines changed

22 files changed

+503
-0
lines changed

‎docs/docs-ref-autogen/outlook/outlook/office.attachmentdetailscompose.yml‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,39 @@ properties:
120120
type: >-
121121
<xref uid="outlook!Office.MailboxEnums.AttachmentType:enum" /> |
122122
string
123+
- name: contentId
124+
uid: outlook!Office.AttachmentDetailsCompose#contentId:member
125+
package: outlook!
126+
fullName: contentId
127+
summary: Gets the content identifier of an inline attachment.
128+
remarks: >-
129+
**Important**:
130+
131+
132+
- The `contentId` property is only supported in Outlook on the web and the
133+
new Outlook on Windows.
134+
135+
136+
- Starting November 15, 2025, changes to how inline images are represented
137+
in the HTML body of Outlook emails in Outlook on the web and the new
138+
Outlook on Windows will begin rolling out to production users. Previously,
139+
the attachment ID of the image appeared in the `src` attribute of the
140+
applicable `<img>` element. After the change, the image will be
141+
represented by a content ID (`cid`<!-- -->) in the `src` attribute
142+
instead. As a result, you'll need to update your add-in's parsing logic if
143+
you parse the attachment ID from the HTML editor or get the Base64 value
144+
of the image from the URL in the `src` attribute. For more information,
145+
see [Changes to inline image representation in Outlook on the web and new
146+
Outlook for
147+
Windows](https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook)<!--
148+
-->.
149+
150+
isPreview: false
151+
isDeprecated: false
152+
syntax:
153+
content: 'contentId: string;'
154+
return:
155+
type: string
123156
- name: id
124157
uid: outlook!Office.AttachmentDetailsCompose#id:member
125158
package: outlook!

‎docs/docs-ref-autogen/outlook_1_10/outlook/office.attachmentdetailscompose.yml‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,42 @@ properties:
120120
type: >-
121121
<xref uid="outlook!Office.MailboxEnums.AttachmentType:enum" /> |
122122
string
123+
- name: contentId
124+
uid: outlook!Office.AttachmentDetailsCompose#contentId:member
125+
package: outlook!
126+
fullName: contentId
127+
summary: >-
128+
Gets the content identifier of an inline attachment.
129+
130+
131+
**Important**:
132+
133+
134+
- The `contentId` property is only supported in Outlook on the web and the
135+
new Outlook on Windows.
136+
137+
138+
- Starting November 15, 2025, changes to how inline images are represented
139+
in the HTML body of Outlook emails in Outlook on the web and the new
140+
Outlook on Windows will begin rolling out to production users. Previously,
141+
the attachment ID of the image appeared in the `src` attribute of the
142+
applicable `<img>` element. After the change, the image will be
143+
represented by a content ID (`cid`<!-- -->) in the `src` attribute
144+
instead. As a result, you'll need to update your add-in's parsing logic if
145+
you parse the attachment ID from the HTML editor or get the Base64 value
146+
of the image from the URL in the `src` attribute. For more information,
147+
see [Changes to inline image representation in Outlook on the web and new
148+
Outlook for
149+
Windows](https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook)<!--
150+
-->.
151+
remarks: ''
152+
153+
isPreview: false
154+
isDeprecated: false
155+
syntax:
156+
content: 'contentId: string;'
157+
return:
158+
type: string
123159
- name: id
124160
uid: outlook!Office.AttachmentDetailsCompose#id:member
125161
package: outlook!

‎docs/docs-ref-autogen/outlook_1_11/outlook/office.attachmentdetailscompose.yml‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,42 @@ properties:
120120
type: >-
121121
<xref uid="outlook!Office.MailboxEnums.AttachmentType:enum" /> |
122122
string
123+
- name: contentId
124+
uid: outlook!Office.AttachmentDetailsCompose#contentId:member
125+
package: outlook!
126+
fullName: contentId
127+
summary: >-
128+
Gets the content identifier of an inline attachment.
129+
130+
131+
**Important**:
132+
133+
134+
- The `contentId` property is only supported in Outlook on the web and the
135+
new Outlook on Windows.
136+
137+
138+
- Starting November 15, 2025, changes to how inline images are represented
139+
in the HTML body of Outlook emails in Outlook on the web and the new
140+
Outlook on Windows will begin rolling out to production users. Previously,
141+
the attachment ID of the image appeared in the `src` attribute of the
142+
applicable `<img>` element. After the change, the image will be
143+
represented by a content ID (`cid`<!-- -->) in the `src` attribute
144+
instead. As a result, you'll need to update your add-in's parsing logic if
145+
you parse the attachment ID from the HTML editor or get the Base64 value
146+
of the image from the URL in the `src` attribute. For more information,
147+
see [Changes to inline image representation in Outlook on the web and new
148+
Outlook for
149+
Windows](https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook)<!--
150+
-->.
151+
remarks: ''
152+
153+
isPreview: false
154+
isDeprecated: false
155+
syntax:
156+
content: 'contentId: string;'
157+
return:
158+
type: string
123159
- name: id
124160
uid: outlook!Office.AttachmentDetailsCompose#id:member
125161
package: outlook!

‎docs/docs-ref-autogen/outlook_1_12/outlook/office.attachmentdetailscompose.yml‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,42 @@ properties:
120120
type: >-
121121
<xref uid="outlook!Office.MailboxEnums.AttachmentType:enum" /> |
122122
string
123+
- name: contentId
124+
uid: outlook!Office.AttachmentDetailsCompose#contentId:member
125+
package: outlook!
126+
fullName: contentId
127+
summary: >-
128+
Gets the content identifier of an inline attachment.
129+
130+
131+
**Important**:
132+
133+
134+
- The `contentId` property is only supported in Outlook on the web and the
135+
new Outlook on Windows.
136+
137+
138+
- Starting November 15, 2025, changes to how inline images are represented
139+
in the HTML body of Outlook emails in Outlook on the web and the new
140+
Outlook on Windows will begin rolling out to production users. Previously,
141+
the attachment ID of the image appeared in the `src` attribute of the
142+
applicable `<img>` element. After the change, the image will be
143+
represented by a content ID (`cid`<!-- -->) in the `src` attribute
144+
instead. As a result, you'll need to update your add-in's parsing logic if
145+
you parse the attachment ID from the HTML editor or get the Base64 value
146+
of the image from the URL in the `src` attribute. For more information,
147+
see [Changes to inline image representation in Outlook on the web and new
148+
Outlook for
149+
Windows](https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook)<!--
150+
-->.
151+
remarks: ''
152+
153+
isPreview: false
154+
isDeprecated: false
155+
syntax:
156+
content: 'contentId: string;'
157+
return:
158+
type: string
123159
- name: id
124160
uid: outlook!Office.AttachmentDetailsCompose#id:member
125161
package: outlook!

‎docs/docs-ref-autogen/outlook_1_13/outlook/office.attachmentdetailscompose.yml‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,42 @@ properties:
120120
type: >-
121121
<xref uid="outlook!Office.MailboxEnums.AttachmentType:enum" /> |
122122
string
123+
- name: contentId
124+
uid: outlook!Office.AttachmentDetailsCompose#contentId:member
125+
package: outlook!
126+
fullName: contentId
127+
summary: >-
128+
Gets the content identifier of an inline attachment.
129+
130+
131+
**Important**:
132+
133+
134+
- The `contentId` property is only supported in Outlook on the web and the
135+
new Outlook on Windows.
136+
137+
138+
- Starting November 15, 2025, changes to how inline images are represented
139+
in the HTML body of Outlook emails in Outlook on the web and the new
140+
Outlook on Windows will begin rolling out to production users. Previously,
141+
the attachment ID of the image appeared in the `src` attribute of the
142+
applicable `<img>` element. After the change, the image will be
143+
represented by a content ID (`cid`<!-- -->) in the `src` attribute
144+
instead. As a result, you'll need to update your add-in's parsing logic if
145+
you parse the attachment ID from the HTML editor or get the Base64 value
146+
of the image from the URL in the `src` attribute. For more information,
147+
see [Changes to inline image representation in Outlook on the web and new
148+
Outlook for
149+
Windows](https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook)<!--
150+
-->.
151+
remarks: ''
152+
153+
isPreview: false
154+
isDeprecated: false
155+
syntax:
156+
content: 'contentId: string;'
157+
return:
158+
type: string
123159
- name: id
124160
uid: outlook!Office.AttachmentDetailsCompose#id:member
125161
package: outlook!

‎docs/docs-ref-autogen/outlook_1_14/outlook/office.attachmentdetailscompose.yml‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,42 @@ properties:
120120
type: >-
121121
<xref uid="outlook!Office.MailboxEnums.AttachmentType:enum" /> |
122122
string
123+
- name: contentId
124+
uid: outlook!Office.AttachmentDetailsCompose#contentId:member
125+
package: outlook!
126+
fullName: contentId
127+
summary: >-
128+
Gets the content identifier of an inline attachment.
129+
130+
131+
**Important**:
132+
133+
134+
- The `contentId` property is only supported in Outlook on the web and the
135+
new Outlook on Windows.
136+
137+
138+
- Starting November 15, 2025, changes to how inline images are represented
139+
in the HTML body of Outlook emails in Outlook on the web and the new
140+
Outlook on Windows will begin rolling out to production users. Previously,
141+
the attachment ID of the image appeared in the `src` attribute of the
142+
applicable `<img>` element. After the change, the image will be
143+
represented by a content ID (`cid`<!-- -->) in the `src` attribute
144+
instead. As a result, you'll need to update your add-in's parsing logic if
145+
you parse the attachment ID from the HTML editor or get the Base64 value
146+
of the image from the URL in the `src` attribute. For more information,
147+
see [Changes to inline image representation in Outlook on the web and new
148+
Outlook for
149+
Windows](https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook)<!--
150+
-->.
151+
remarks: ''
152+
153+
isPreview: false
154+
isDeprecated: false
155+
syntax:
156+
content: 'contentId: string;'
157+
return:
158+
type: string
123159
- name: id
124160
uid: outlook!Office.AttachmentDetailsCompose#id:member
125161
package: outlook!

‎docs/docs-ref-autogen/outlook_1_15/outlook/office.attachmentdetailscompose.yml‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,42 @@ properties:
120120
type: >-
121121
<xref uid="outlook!Office.MailboxEnums.AttachmentType:enum" /> |
122122
string
123+
- name: contentId
124+
uid: outlook!Office.AttachmentDetailsCompose#contentId:member
125+
package: outlook!
126+
fullName: contentId
127+
summary: >-
128+
Gets the content identifier of an inline attachment.
129+
130+
131+
**Important**:
132+
133+
134+
- The `contentId` property is only supported in Outlook on the web and the
135+
new Outlook on Windows.
136+
137+
138+
- Starting November 15, 2025, changes to how inline images are represented
139+
in the HTML body of Outlook emails in Outlook on the web and the new
140+
Outlook on Windows will begin rolling out to production users. Previously,
141+
the attachment ID of the image appeared in the `src` attribute of the
142+
applicable `<img>` element. After the change, the image will be
143+
represented by a content ID (`cid`<!-- -->) in the `src` attribute
144+
instead. As a result, you'll need to update your add-in's parsing logic if
145+
you parse the attachment ID from the HTML editor or get the Base64 value
146+
of the image from the URL in the `src` attribute. For more information,
147+
see [Changes to inline image representation in Outlook on the web and new
148+
Outlook for
149+
Windows](https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook)<!--
150+
-->.
151+
remarks: ''
152+
153+
isPreview: false
154+
isDeprecated: false
155+
syntax:
156+
content: 'contentId: string;'
157+
return:
158+
type: string
123159
- name: id
124160
uid: outlook!Office.AttachmentDetailsCompose#id:member
125161
package: outlook!

‎docs/docs-ref-autogen/outlook_1_8/outlook/office.attachmentdetailscompose.yml‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,42 @@ properties:
120120
type: >-
121121
<xref uid="outlook!Office.MailboxEnums.AttachmentType:enum" /> |
122122
string
123+
- name: contentId
124+
uid: outlook!Office.AttachmentDetailsCompose#contentId:member
125+
package: outlook!
126+
fullName: contentId
127+
summary: >-
128+
Gets the content identifier of an inline attachment.
129+
130+
131+
**Important**:
132+
133+
134+
- The `contentId` property is only supported in Outlook on the web and the
135+
new Outlook on Windows.
136+
137+
138+
- Starting November 15, 2025, changes to how inline images are represented
139+
in the HTML body of Outlook emails in Outlook on the web and the new
140+
Outlook on Windows will begin rolling out to production users. Previously,
141+
the attachment ID of the image appeared in the `src` attribute of the
142+
applicable `<img>` element. After the change, the image will be
143+
represented by a content ID (`cid`<!-- -->) in the `src` attribute
144+
instead. As a result, you'll need to update your add-in's parsing logic if
145+
you parse the attachment ID from the HTML editor or get the Base64 value
146+
of the image from the URL in the `src` attribute. For more information,
147+
see [Changes to inline image representation in Outlook on the web and new
148+
Outlook for
149+
Windows](https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook)<!--
150+
-->.
151+
remarks: ''
152+
153+
isPreview: false
154+
isDeprecated: false
155+
syntax:
156+
content: 'contentId: string;'
157+
return:
158+
type: string
123159
- name: id
124160
uid: outlook!Office.AttachmentDetailsCompose#id:member
125161
package: outlook!

‎docs/docs-ref-autogen/outlook_1_9/outlook/office.attachmentdetailscompose.yml‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,42 @@ properties:
120120
type: >-
121121
<xref uid="outlook!Office.MailboxEnums.AttachmentType:enum" /> |
122122
string
123+
- name: contentId
124+
uid: outlook!Office.AttachmentDetailsCompose#contentId:member
125+
package: outlook!
126+
fullName: contentId
127+
summary: >-
128+
Gets the content identifier of an inline attachment.
129+
130+
131+
**Important**:
132+
133+
134+
- The `contentId` property is only supported in Outlook on the web and the
135+
new Outlook on Windows.
136+
137+
138+
- Starting November 15, 2025, changes to how inline images are represented
139+
in the HTML body of Outlook emails in Outlook on the web and the new
140+
Outlook on Windows will begin rolling out to production users. Previously,
141+
the attachment ID of the image appeared in the `src` attribute of the
142+
applicable `<img>` element. After the change, the image will be
143+
represented by a content ID (`cid`<!-- -->) in the `src` attribute
144+
instead. As a result, you'll need to update your add-in's parsing logic if
145+
you parse the attachment ID from the HTML editor or get the Base64 value
146+
of the image from the URL in the `src` attribute. For more information,
147+
see [Changes to inline image representation in Outlook on the web and new
148+
Outlook for
149+
Windows](https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook)<!--
150+
-->.
151+
remarks: ''
152+
153+
isPreview: false
154+
isDeprecated: false
155+
syntax:
156+
content: 'contentId: string;'
157+
return:
158+
type: string
123159
- name: id
124160
uid: outlook!Office.AttachmentDetailsCompose#id:member
125161
package: outlook!

‎docs/includes/outlook-1_8.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@
2525
|[AttachmentContent](/javascript/api/outlook/office.attachmentcontent)|[content](/javascript/api/outlook/office.attachmentcontent#outlook-office-attachmentcontent-content-member)|The content of an attachment as a string.|
2626
||[format](/javascript/api/outlook/office.attachmentcontent#outlook-office-attachmentcontent-format-member)|The string format to use for an attachment's content.|
2727
|[AttachmentDetailsCompose](/javascript/api/outlook/office.attachmentdetailscompose)|[attachmentType](/javascript/api/outlook/office.attachmentdetailscompose#outlook-office-attachmentdetailscompose-attachmenttype-member)|Gets a value that indicates the attachment's type.|
28+
||[contentId](/javascript/api/outlook/office.attachmentdetailscompose#outlook-office-attachmentdetailscompose-contentid-member)|Gets the content identifier of an inline attachment.|
2829
||[id](/javascript/api/outlook/office.attachmentdetailscompose#outlook-office-attachmentdetailscompose-id-member)|Gets the index of the attachment.|
2930
||[isInline](/javascript/api/outlook/office.attachmentdetailscompose#outlook-office-attachmentdetailscompose-isinline-member)|Gets a value that indicates whether the attachment appears as an image in the body of the item instead of in the attachment list.|
3031
||[name](/javascript/api/outlook/office.attachmentdetailscompose#outlook-office-attachmentdetailscompose-name-member)|Gets the name of the attachment.|

0 commit comments

Comments
 (0)